Beam failure recovery method and device

ABSTRACT

A beam failure recovery method and device are provided. The method includes: after a beam failure event or a beam failure recovery event is triggered, monitoring a physical downlink control channel (PDCCH) scrambled with a C-RNTI in a first CORESET for beam failure recovery; and/or monitoring a PDCCH scrambled with a C-RNTI in a second CORESET, where resources corresponding to the first CORESET are different from resources corresponding to the second CORESET.

CROSS-REFERENCE TO RELATED APPLICATION

The present application is a U.S. national phase application of a PCTApplication No. PCT/CN2019/074175 filed on Jan. 31, 2019, which claims apriority to Chinese Patent Application No. 201810147514.8 filed inChina, on Feb. 12, 2018, disclosures of which are incorporated in theirentireties by reference herein.

TECHNICAL FIELD

The present disclosure relates to the field of telecommunicationtechnology, in particular to a beam failure recovery method and device.

BACKGROUND

In the related art, after a beam failure is triggered, user equipment(UE) no longer monitors a beam or a control channel resource set(CORESET) of reference signal (RS) corresponding to the beam, except fora candidate beam or an RS resource corresponding to the candidate beam,for a cell radio network temporary identifier (C-RNTI).

SUMMARY

An objective of some embodiments of the present disclosure is to providea beam failure recovery method and device, to resolve the problem as towhether UE needs to monitor a physical downlink control channel (PDCCH)scrambled with a C-RNTI in a specified CORESET in a beam failurerecovery procedure.

In a first aspect, a beam failure recovery method is provided,including:

after a beam failure event or a beam failure recovery event istriggered, monitoring a PDCCH scrambled with a C-RNTI in a first CORESETfor beam failure recovery; and/or monitoring a PDCCH scrambled with aC-RNTI in a second CORESET,

where resources corresponding to the first CORESET are different fromresources corresponding to the second CORESET.

In a second aspect, UE is further provided, including:

a first monitoring module, configured to: after a beam failure event ora beam failure recovery event is triggered, monitor a PDCCH scrambledwith a C-RNTI in a first CORESET for beam failure recovery; and/or

a second monitoring module, configured to: after a beam failure event ora beam failure recovery event is triggered, monitor a PDCCH scrambledwith a C-RNTI in a second CORESET,

where resources corresponding to the first CORESET are different fromresources corresponding to the second CORESET.

In a third aspect, UE is further provided, including: a processor, astorage, and a computer program stored in the storage and configured tobe executed by the processor, where the processor is configured toexecute the computer program to implement the steps in the foregoingbeam failure recovery method.

In a fourth aspect, a computer-readable storage medium storing therein acomputer program is further provided, where the computer program isconfigured to be executed by a processor to implement the steps in theforegoing beam failure recovery method.

In this way, after a beam failure, a beam failure event, beam failurerecovery or a beam failure recovery event is triggered, a PDCCHscrambled with a C-RNTI is monitored in a first CORESET for beam failurerecovery; and/or a PDCCH scrambled with a C-RNTI is monitored in asecond CORESET, where resources corresponding to the first CORESET aredifferent from resources corresponding to the second CORESET. Thus, theproblem as to whether UE needs to monitor a PDCCH scrambled with aC-RNTI in a specified CORESET in a beam failure recovery procedure isresolved.

BRIEF DESCRIPTION OF THE DRAWINGS

Various other advantages and benefits will become more obvious topersons of ordinary skill in the art by reading detailed description ofthe following optional implementations. The accompanying drawings areonly used for describing the optional implementations, and should not beconsidered as a limitation on the present disclosure. The same referencenumerals represent the same components throughout the accompanyingdrawings. In the accompanying drawings:

FIG. 1 is a schematic diagram of a beam failure recovery method of UE inthe related art;

FIG. 2 is a schematic diagram of an architecture of a wirelesscommunication system according to some embodiments of the presentdisclosure;

FIG. 3 is a first flowchart of a beam failure recovery method accordingto some embodiments of the present disclosure;

FIG. 4 is a second flowchart of a beam failure recovery method accordingto some embodiments of the present disclosure;

FIG. 5 is a third flowchart of a beam failure recovery method accordingto some embodiments of the present disclosure;

FIG. 6 is a first schematic structural diagram of UE according to someembodiments of the present disclosure;

FIG. 7 is a second schematic structural diagram of UE according to someembodiments of the present disclosure;

FIG. 8 is a third schematic structural diagram of UE according to someembodiments of the present disclosure.

DETAILED DESCRIPTION

The following clearly and completely describes the technical solutionsin some embodiments of the present disclosure with reference to theaccompanying drawings in some embodiments of the present disclosure.Apparently, the described embodiments are merely some rather than all ofthe embodiments of the present disclosure. All other embodimentsobtained by persons of ordinary skill in the art based on theembodiments of the present disclosure without creative efforts fallwithin the scope of the present disclosure.

The term “include” or “comprise” or any variation thereof in thedescription and claims of the present application is intended toencompass a non-exclusive inclusion. For example, a procedure, method,system, product or device that includes a series of steps or units isnot necessarily limited to those steps or units specified expressly,rather, may include other steps or units that are not specifiedexpressly or are inherent to the procedure, method, system, product ordevice. In addition, the term “and/or” used in the description andclaims represents at least one of associated objects. For example, Aand/or B represents the following three cases: only A exists, only Bexists, and both A and B exist.

In some embodiments of the present disclosure, the terms such as “forexample” are used to represent examples, illustrations or descriptions.In some embodiments of the present disclosure, any embodiment or designscheme limited with “for example” should not be construed to be morepreferred than or superior over other embodiments or design schemes.Rather, the terms such as “for example” are used to specifically presentrelated concepts.

In a future fifth-generation (5G) mobile communication system, toachieve the objective of a downlink transmission rate of 20 Gbps and anuplink transmission rate of 10 Gbps, high-frequency communication andmassive multiple input multiple output (MIMO) technologies will beadopted. The high-frequency communication may provide a wider systembandwidth, and a smaller antenna size which further facilitates thedeployment of massive MIMO in base station and UE. The high-frequencycommunication has disadvantages such as relatively high path loss, poorinterference immunity, and frail link. The massive MIMO technology canprovide relatively high antenna gain. Therefore, the combination of thehigh-frequency communication and the massive MIMO technology becomes theinexorable trend of a future 5G mobile communication system. However,the massive MIMO technology cannot resolve all problems in thehigh-frequency communication, for example, link fragility. When anobstacle is encountered in the high-frequency communication, a beamfailure recovery mechanism can quickly switch beams, that is, switch acommunication link from a poor-quality beam to a desirable beam, toavoid a radio link failure, thereby effectively improving the linkrobustness.

In the meeting of the 3rd Generation Partnership Project (3GPP) RadioAccess Network (RAN) 1, the following conclusion about a beam failurerecovery mechanism of UE is reached.

Referring to FIG. 1, FIG. 1 shows specific steps of the beam failurerecovery mechanism of UE as follows:

A Step 101: detecting a beam failure;

A Step 102: identifying a new candidate beam;

A Step 103: transmitting a beam failure recovery request;

A Step 104: monitoring, by the UE, a response of next-generation nodebase station (gNB) to the beam failure recovery request.

It needs to be noted that the identification of a new candidate beam maybe performed before or after the detection of the beam failure.

In the 3GPP RAN1 meeting, the following conclusion about thetransmission of a beam failure recovery request by UE is reached:

The transmission of a beam failure recovery request on a contention-freephysical random access channel (PRACH) is supported. A PRACH resourceused for transmitting a beam failure recovery request is orthogonal toresources of regular PRACHs, at least for the frequency divisionmultiplexing (FDM) case;

Other ways of achieving orthogonality, e.g., code division multiplexing(CDM) or time division multiplexing (TDM) are for future study;

Whether or not to adopt different sequence or format is for futurestudy; Whether or not the retransmission of a beam failure recoveryrequest is similar to regular PRACH retransmission is for future study;

The transmission of a beam failure recovery request on a physical uplinkcontrol channel (PUCCH) is supported;

Whether or not a PUCCH is transmitted with beam sweeping is for futurestudy;

Whether or not to use contention-based PRACH as a supplement tocontention-free PRACH for transmission of beam failure recovery requestis for future study;

Contention-based PRACH resources are selected from a conventional randomaccess channel (RACH) resource pool;

A four-step RACH procedure is used.

The embodiments of the present disclosure are described below withreference to the accompanying drawings. The beam failure recovery methodand device provided in some embodiments of the present disclosure may beapplied to a wireless communication system. The wireless communicationsystem may be a system using 5G mobile communication technology(referred to as 5G system below) or an evolved Long Term Evolution(eLTE) system or a future evolved communication system. Referring toFIG. 2, FIG. 2 is a schematic diagram of an architecture of a wirelesscommunication system according to some embodiments of the presentdisclosure. As shown in FIG. 2, the wireless communication system mayinclude a network side device 20 and UE. For example, the UE is denotedas UE 21. The UE 21 may communicate with the network side device 20.During actual application, the connection between foregoing devices maybe a wireless connection. To illustrate connection relationships betweenthe devices easily and intuitively, solid lines are used to representthe connection relationships in FIG. 2.

It needs to be noted that the communication system may include aplurality of UEs. The network side device may communicate with theplurality of UEs (signaling or data transmission).

The network side device provided in some embodiments of the presentdisclosure may be a base station. The network side device may be acommonly used base station or may be an evolved node base station (eNB)or may be a device in a 5G system such as a network side device (forexample, a gNB) or a transmission and reception point (TRP).

The UE provided in some embodiments of the present disclosure may be amobile phone, a tablet computer, a notebook computer, an ultra-mobilepersonal computer (UMPC), a netbook, a personal digital assistant (PDA)or the like.

Referring to FIG. 3, FIG. 3 shows a procedure of a beam failure recoverymethod according to some embodiments of the present disclosure. Themethod is performed by UE and has the following specific step.

A step 301 includes: after a beam failure event or a beam failurerecovery event is triggered, monitoring a PDCCH scrambled with a C-RNTIin a first CORESET for beam failure recovery; and/or monitoring a PDCCHscrambled with a C-RNTI in a second CORESET.

Resources corresponding to the first CORESET are different fromresources corresponding to the second CORESET.

It needs to be noted that the beam failure event may also be referred toas beam failure, and the beam failure recovery event may also bereferred to as beam failure recovery.

In some embodiments of the present disclosure, the first CORESET may bereferred to as a CORESET of preset resources corresponding to beamfailure recovery, and the second CORESET may be referred to as a CORESETcorresponding to resources other than the preset resources. The presetresources include: some or all candidate beams, or RS resourcescorresponding to candidate beams, or candidate RS resources.

In some embodiments of the present disclosure, optionally, the methodfurther includes: stopping monitoring a PDCCH scrambled with a C-RNTI inthe second CORESET when a C-RNTI is monitored in the first CORESET; orstopping monitoring a PDCCH scrambled with a C-RNTI in the first CORESETwhen a C-RNTI is monitored in the second CORESET.

In some embodiments of the present disclosure, optionally, the resourcescorresponding to the first CORESET include at least one of:

all candidate beams;

RS resources corresponding to all candidate beams;

some candidate beams;

RS resources corresponding to some candidate beams;

a candidate RS resource; or

a candidate RS resource corresponding to a candidate beam.

In some embodiments of the present disclosure, optionally, before thestep 301, the method further includes: indicating, by a media accesscontrol (MAC) layer, a beam failure indication to a physical (PHY)layer.

In some embodiments of the present disclosure, optionally, before thestep 301, the method further includes: transmitting a random accesspreamble to a network side device by using a random access procedure,where the random access preamble is used as a beam failure recoveryrequest; or indicating, by a PHY layer, a candidate beam or a resourcecorresponding to a candidate beam or a candidate resource to an MAClayer, where the resource includes an RS resource or candidate RSresource.

In some embodiments of the present disclosure, optionally, before thetransmitting a random access preamble to the network side device byusing a random access procedure or before the indicating, by the PHYlayer, the candidate beam or the resource corresponding to the candidatebeam or the candidate resource to the MAC layer, the method furtherincludes at least one of: stopping a beam failure recovery timer;stopping a beam failure recovery request transmission counter; orstopping transmitting a random access preamble to the network sidedevice.

In some embodiments of the present disclosure, optionally, after thetransmitting a random access preamble to the network side device byusing a random access procedure so as to transmit a beam failurerecovery request or after the indicating, by the PHY layer, thecandidate beam or the resource corresponding to the candidate beam orthe candidate resource to the MAC layer, the method further includes atleast one of: stopping a beam failure recovery timer; stopping a beamfailure recovery request transmission counter; stopping transmitting arandom access preamble to the network side device; or indicating to thenetwork side device that beam failure recovery succeeds.

In some embodiments of the present disclosure, optionally, in the step301, when a C-RNTI is monitored in the second CORESET, the methodfurther includes at least one of: continuing a beam failure recoveryprocedure; continuing a random access procedure in a beam failurerecovery procedure; or indicating, by a PHY layer, a new candidate beamor candidate RS resource to an MAC layer.

The new candidate beam is a beam in the second CORESET in which a C-RNTIis monitored; or the new candidate RS resource is an RS resource in thesecond CORESET in which a C-RNTI is monitored.

In some embodiments of the present disclosure, optionally, whenindicating by the PHY layer to the higher layer, the method furtherincludes at least one of: stopping a beam failure recovery procedure; orstopping a random access procedure in a beam failure recovery procedure.

In some embodiments of the present disclosure, optionally, in the step301, when a C-RNTI is monitored in the first CORESET, the method furtherincludes at least one of:

stopping a beam failure recovery procedure;

stopping a random access procedure in a beam failure recovery procedure;

determining that beam failure recovery succeeds;

indicating, by an MAC layer to a higher layer and/or a PHY layer, thatbeam failure recovery succeeds;

stopping a beam failure recovery timer;

stopping a beam failure recovery request transmission counter; orstopping transmitting a random access preamble to a network side device.

Referring to FIG. 4, FIG. 4 shows a procedure of a beam failure recoverymethod according to some embodiments of the present disclosure. Themethod is performed by UE and includes the following specific steps.

A step 401 includes: after a beam failure event or a beam failurerecovery event is triggered, monitoring a PDCCH scrambled with a C-RNTIin a first CORESET for beam failure recovery; and/or monitoring a PDCCHscrambled with a C-RNTI in a second CORESET.

Resources corresponding to the first CORESET are different fromresources corresponding to the second CORESET.

A step 402 includes: discarding a C-RNTI when the C-RNTI is monitored inthe first CORESET, and continuing monitoring a C-RNTI in the secondCORESET; or discarding a C-RNTI when the C-RNTI is monitored in thesecond CORESET, and continuing monitoring a C-RNTI in the first CORESET.

In some embodiments of the present disclosure, optionally, the methodfurther includes: stopping monitoring a PDCCH scrambled with a C-RNTI inthe second CORESET when a C-RNTI is monitored in the first CORESET; orstopping monitoring a PDCCH scrambled with a C-RNTI in the first CORESETwhen a C-RNTI is monitored in the second CORESET.

In some embodiments of the present disclosure, optionally, the resourcescorresponding to the first CORESET include at least one of:

all candidate beams;

RS resources corresponding to all candidate beams;

some candidate beams;

RS resources corresponding to some candidate beams;

a candidate RS resource; or

a candidate RS resource corresponding to a candidate beam.

In some embodiments of the present disclosure, optionally, before thestep 401, the method further includes: indicating, by an MAC layer, abeam failure indication to a PHY layer.

In some embodiments of the present disclosure, optionally, before thestep 401, the method further includes: transmitting a random accesspreamble to a network side device by using a random access procedure,where the random access preamble is used as a beam failure recoveryrequest; or indicating, by a PHY layer, a candidate beam or a resourcecorresponding to a candidate beam or a candidate resource to an MAClayer, where the resource includes an RS resource or candidate RSresource.

In some embodiments of the present disclosure, optionally, before thetransmitting a random access preamble to the network side device byusing a random access procedure or before the indicating, by the PHYlayer, the candidate beam or the resource corresponding to the candidatebeam or the candidate resource to the MAC layer, the method furtherincludes at least one of: stopping a beam failure recovery timer;stopping a beam failure recovery request transmission counter; orstopping transmitting a random access preamble to the network sidedevice.

In some embodiments of the present disclosure, optionally, after thetransmitting a random access preamble to the network side device byusing a random access procedure so as to transmit a beam failurerecovery request or after the indicating, by the PHY layer, thecandidate beam or the resource corresponding to the candidate beam orthe candidate resource to the MAC layer, the method further includes atleast one of: stopping a beam failure recovery timer; stopping a beamfailure recovery request transmission counter; stopping transmitting arandom access preamble to the network side device; or indicating to thenetwork side device that beam failure recovery succeeds.

In some embodiments of the present disclosure, optionally, in the step401, when a C-RNTI is monitored in the second CORESET, the methodfurther includes at least one of: continuing a beam failure recoveryprocedure; continuing a random access procedure in a beam failurerecovery procedure; or indicating, by a PHY layer, a new candidate beamor candidate RS resource to an MAC layer.

The new candidate beam is a beam in the second CORESET in which a C-RNTIis monitored; or the new candidate RS resource is an RS resource in thesecond CORESET in which a C-RNTI is monitored.

In some embodiments of the present disclosure, optionally, whenindicating by the PHY layer to the higher layer, the method furtherincludes at least one of: stopping a beam failure recovery procedure; orstopping a random access procedure in a beam failure recovery procedure.

In some embodiments of the present disclosure, optionally, in the step401, when a C-RNTI is monitored in the first CORESET, the method furtherincludes at least one of:

stopping a beam failure recovery procedure;

stopping a random access procedure in a beam failure recovery procedure;

determining that beam failure recovery succeeds;

indicating, by an MAC layer to a higher layer and/or a PHY layer, thatbeam failure recovery succeeds;

stopping a beam failure recovery timer;

stopping a beam failure recovery request transmission counter; or

stopping transmitting a random access preamble to a network side device.

Referring to FIG. 5, FIG. 5 shows a procedure of a beam failure recoverymethod according to some embodiments of the present disclosure. Themethod is performed by UE and includes the following specific steps.

A step 501 includes: after a beam failure event or a beam failurerecovery event is triggered, monitoring a PDCCH scrambled with a C-RNTIin a first CORESET for beam failure recovery; and/or monitoring a PDCCHscrambled with a C-RNTI in a second CORESET.

Resources corresponding to the first CORESET are different fromresources corresponding to the second CORESET.

A step 502 includes: in a beam failure recovery procedure, whencontention-free random access (CFRA) fails, declaring that beam failurerecovery fails or continuing a random access procedure of beam failurerecovery by using contention-based random access (CBRA).

A step 503 includes: in a beam failure recovery procedure, when CFRAfails and no indication of a candidate beam and/or candidate resourcefrom a PHY layer is received, declaring that beam failure recovery failsor continuing a random access procedure of beam failure recovery byusing CBRA.

A step 504 includes: if a beam failure recovery timer expires in a beamfailure recovery procedure and/or a preamble transmission or beamfailure recovery request transmission counter counts to a maximum valuein a beam failure recovery procedure, declaring that beam failurerecovery fails.

It needs to be noted that the execution order of steps 501, 502, 503,and 504 is not limited in some embodiments of the present disclosure.

In some embodiments of the present disclosure, optionally, after it isdetermined that beam failure recovery fails and/or an indication of acandidate beam and/or candidate resource from a PHY layer is received,the method further includes starting at least one of:

a beam failure recovery timer;

a beam failure recovery request transmission counter;

a CFRA-based beam failure recovery timer;

a CFRA-based beam failure recovery request transmission counter;

a CBRA-based beam failure recovery timer; or

a CBRA-based beam failure recovery request transmission counter.

In some embodiments of the present disclosure, optionally, the methodfurther includes:

in the process of continuing a random access procedure of beam failurerecovery by using CBRA, if a CBRA timer expires, and/or a CBRA preambletransmission or beam failure recovery request transmission countercounts to a maximum value, declaring that beam failure recovery fails.

In some embodiments of the present disclosure, optionally, the methodfurther includes:

when a C-RNTI is monitored in the first CORESET or the second CORESETbefore a beam failure recovery timer expires, determining that beamfailure recovery succeeds; and/or

when a C-RNTI is monitored in the first CORESET or the second CORESETbefore a preamble transmission counter or a beam failure recoveryrequest transmission counter counts to a maximum value during beamfailure recovery, determining that beam failure recovery succeeds.

In some embodiments of the present disclosure, optionally, the methodfurther includes: when beam failure recovery fails or beam failurerecovery succeeds, indicating, to a PHY layer and/or a higher layer,that beam failure recovery fails or beam failure recovery succeeds.

In some embodiments of the present disclosure, optionally, the methodfurther includes:

when an MAC layer determines that beam failure recovery succeeds or beamfailure recovery fails, indicating, to a radio resource control (RRC)layer, indication information indicating that beam failure recoverysucceeds or beam failure recovery fails, where the indicationinformation is used in the RRC layer for instructing the RRC layer toadjust radio link monitoring (RLM).

Example 1: monitoring two C-RNTIs, and possibly discarding onesubsequently.

After a beam failure event or a beam failure recovery event istriggered, UE performs at least one of following operations:

(1) monitoring a PDCCH scrambled with a C-RNTI in a first CORESET forbeam failure recovery;

(2) monitoring a PDCCH scrambled with a C-RNTI in a second CORESET.

Further, before the UE performs the operations (1) and (2), an MAC layerindicates a beam failure indication to a PHY layer. After receiving theindication, the PHY layer then performs the operations (1) and (2).

Further, before the UE performs the operations (1) and (2), the UEtransmits at the MAC layer a beam failure recovery request to a basestation by using a random access procedure. After transmitting a randomaccess preamble in a random access procedure or indicating, by a PHYlayer, a candidate beam or an RS resource corresponding to a candidatebeam or a candidate RS resource to the MAC layer, the UE performs theoperations (1) and (2).

Further, after the UE performs the operations (1) or (2):

discarding a C-RNTI when the C-RNTI is monitored in the first CORESET;or

discarding a C-RNTI when the C-RNTI is monitored in the second CORESET.

Example 2: monitoring two C-RNTIs. Further, refraining from transmittinga preamble to a network side device, or monitoring two C-RNTIs aftertransmitting the preamble.

After a beam failure event or a beam failure recovery event istriggered, UE performs at least one of following operations:

(1) monitoring a PDCCH scrambled with a C-RNTI in a first CORESET forbeam failure recovery;

(2) monitoring a PDCCH scrambled with a C-RNTI in a second CORESET.

Scenario 1: When a C-RNTI is monitored in the second CORESET, UEperforms at least one of following operations:

continuing (not stopping) a beam failure recovery procedure;

continuing (not stopping) a random access procedure in a beam failurerecovery procedure; or

indicating, by a PHY layer, a new candidate beam or candidate RSresource to an MAC layer.

Further, the new candidate beam is a beam in the second CORESET in whicha C-RNTI is monitored; or the new candidate RS resource is an RSresource in the second CORESET in which a C-RNTI is monitored.

Scenario 2: When a C-RNTI is monitored in the second CORESET or when aPHY layer determines that beam failure recovery succeeds in the processof monitoring a C-RNTI in the first CORESET or the second CORESET, UEperforms at least one of following operations:

(1) stopping a beam failure recovery procedure, and/or stopping a randomaccess procedure in a beam failure recovery procedure;

(2) indicating, by a PHY layer to a higher layer, that beam failurerecovery succeeds.

Further, after the indication from the PHY layer is received by the MAClayer, a beam failure recovery procedure is stopped and/or a randomaccess procedure in a beam failure recovery procedure is stopped.

For the foregoing operations (1) and (2), before transmitting a randomaccess preamble to the network side device by using a random accessprocedure or before indicating, by the PHY layer, the candidate beam orthe resource corresponding to the candidate beam or the candidateresource to the MAC layer, UE performs at least one of followingoperations:

stopping a beam failure recovery timer;

stopping a beam failure recovery request transmission counter; or

stopping transmitting a random access preamble to the network sidedevice.

For operations (1) and (2), after transmitting a random access preambleto the network side device by using a random access procedure so as totransmit a beam failure recovery request; or after indicating, by thePHY layer, the candidate beam or the resource corresponding to thecandidate beam or the candidate resource to the MAC layer, UE performsat least one of following operations:

stopping a beam failure recovery timer;

stopping a beam failure recovery request transmission counter;

stopping transmitting a random access preamble to the network sidedevice; or

indicating to the network side device that beam failure recoverysucceeds.

Scenario 3: When a C-RNTI is monitored in the first CORESET, UE performsat least one of following operations:

stopping a beam failure recovery procedure;

stopping a random access procedure in a beam failure recovery procedure;

determining that beam failure recovery succeeds;

indicating, by an MAC layer to a higher layer and/or a PHY layer, thatbeam failure recovery succeeds;

stopping a beam failure recovery timer;

stopping a beam failure recovery request transmission counter; orstopping transmitting a random access preamble to a network side device.

Example 3

In a RACH procedure in a beam failure recovery procedure, UE performs atleast one of following operations:

(1) When CFRA fails, the UE directly declares that beam failure recoveryfails, or continues a random access procedure of beam failure recoveryby using CBRA.

That the CFRA fails includes: a CFRA timer expires and/or a CFRA countercounts to a maximum value. That is, in the process of continuing arandom access procedure of beam failure recovery by using CBRA, if aCBRA timer expires and/or a CBRA counter counts to a maximum value, UEdirectly declares that beam failure recovery fails.

(2) When CFRA fails and no indication of a candidate beam and/orcandidate resource from a PHY layer is received, the UE declares thatbeam failure recovery fails or continues a random access procedure ofbeam failure recovery by using CBRA.

(3) If a beam failure recovery timer expires in a beam failure recoveryprocedure and/or a preamble transmission or beam failure recoveryrequest transmission counter counts to a maximum value in a beam failurerecovery procedure, the UE directly declares that beam failure recoveryfails.

Further, after beam failure recovery fails or succeeds as in theforegoing operations (1), (2), and (3), the PHY layer and/or the higherlayer is informed.

Example 4

In all the Example 1, Example 2, and Example 3, after determining thatbeam failure recovery succeeds or fails, the MAC layer indicates, to anRRC layer, that beam failure recovery succeeds or fails. The RRC layeradjusts the RLM according to the indication.

After obtaining the indication that beam failure recovery succeedsindicated by the MAC layer, or indicated by the MAC layer through thePHY layer, the RRC layer uses this indication as an in-sync indication,or if a T310 timer is running, the timer is stopped or the timer isrestarted.

After obtaining the indication that beam failure recovery failsindicated by the MAC layer, or indicated by the MAC layer through thePHY layer, the RRC layer uses this indication as an out-of-syncindication or triggers a radio link failure or starts the T310 timer.

Referring to FIG. 6, the present disclosure provides in some embodimentsUE 600, including:

a first monitoring module 601, configured to: after a beam failure eventor a beam failure recovery event is triggered, monitor a PDCCH scrambledwith a C-RNTI in a first CORESET for beam failure recovery; and/or

a second monitoring module 602, configured to: after a beam failureevent or a beam failure recovery event is triggered, monitor a PDCCHscrambled with a C-RNTI in a second CORESET,

where resources corresponding to the first CORESET are different fromresources corresponding to the second CORESET.

Referring to FIG. 7, the present disclosure provides in some embodimentsanother UE 700, including:

a first monitoring module 601, configured to: after a beam failure eventor a beam failure recovery event is triggered, monitor a PDCCH scrambledwith a C-RNTI in a first CORESET for beam failure recovery; and/or

a second monitoring module 602, configured to: after a beam failureevent or a beam failure recovery event is triggered, monitor a PDCCHscrambled with a C-RNTI in a second CORESET,

where resources corresponding to the first CORESET are different fromresources corresponding to the second CORESET.

Optionally, the UE 700 further includes:

a first discarding module 701, configured to: discard a C-RNTI when theC-RNTI is monitored in the first CORESET, and continue monitoring aC-RNTI in the second CORESET; and/or

a second discarding module 702, configured to: discard a C-RNTI when theC-RNTI is monitored in the second CORESET, and continue monitoring aC-RNTI in the first CORESET.

Optionally, the UE 700 further includes:

a first processing module 703, configured to: stop monitoring a PDCCHscrambled with a C-RNTI in the second CORESET when a C-RNTI is monitoredin the first CORESET; or

stop monitoring a PDCCH scrambled with a C-RNTI in the first CORESETwhen a C-RNTI is monitored in the second CORESET.

Further, the resources corresponding to the first CORESET include atleast one of: all candidate beams; RS resources corresponding to allcandidate beams; some candidate beams; RS resources corresponding tosome candidate beams; a candidate RS resource; or a candidate RSresource corresponding to a candidate beam.

Optionally, the UE 700 further includes:

a first indication module 704, configured to indicate, by an MAC layer,a beam failure indication to a PHY layer.

Optionally, the UE 700 further includes:

a first transmission module 705, configured to: transmit a random accesspreamble to a network side device by using a random access procedure,where the random access preamble is used as a beam failure recoveryrequest; or

a second indication module 706, configured to indicate, by a PHY layer,a candidate beam or a resource corresponding to a candidate beam or acandidate resource to an MAC layer, where the resource includes an RSresource or candidate RS resource.

Optionally, the UE 700 further includes:

a second processing module 707, configured to: when a C-RNTI ismonitored in the second CORESET, continue a beam failure recoveryprocedure; and/or continue a random access procedure in a beam failurerecovery procedure; and/or

a third indication module 708, configured to: when a C-RNTI is monitoredin the second CORESET, indicate, by a PHY layer, a new candidate beam orcandidate RS resource to an MAC layer.

Further, the new candidate beam is a beam in the second CORESET in whicha C-RNTI is monitored; or the new candidate RS resource is an RSresource in the second CORESET in which a C-RNTI is monitored.

Optionally, the UE 700 further includes:

a third processing module 709, configured to: when a C-RNTI is monitoredin the second CORESET or when a PHY layer determines that beam failurerecovery succeeds in the process of monitoring a C-RNTI in the firstCORESET or the second CORESET, stop a beam failure recovery procedure;and/or stop a random access procedure in a beam failure recoveryprocedure; and/or

a fourth indication module 710, configured to: after the UE monitors theC-RNTI or the PHY layer determines that beam failure recovery succeeds,indicate, by the PHY layer to a higher layer, that beam failure recoverysucceeds.

Optionally, the UE 700 further includes:

a fourth processing module 711, configured to: after the higher layerreceives the indication from the PHY layer, stop a beam failure recoveryprocedure, and/or stop a random access procedure in a beam failurerecovery procedure.

Optionally, the UE 700 further includes:

a fifth processing module 712, configured to: before transmitting arandom access preamble to the network side device by using a randomaccess procedure or before indicating, by the PHY layer, the candidatebeam or the resource corresponding to the candidate beam or thecandidate resource to the MAC layer, perform at least one of: stopping abeam failure recovery timer; stopping a beam failure recovery requesttransmission counter; or stopping transmitting a random access preambleto the network side device.

Optionally, the UE 700 further includes:

a sixth processing module 713, configured to: after transmitting arandom access preamble to the network side device by using a randomaccess procedure so as to transmit a beam failure recovery request orafter indicating, by the PHY layer, the candidate beam or the resourcecorresponding to the candidate beam or the candidate resource to the MAClayer, perform at least one of: stopping a beam failure recovery timer;stopping a beam failure recovery request transmission counter; stoppingtransmitting a random access preamble to the network side device; orindicating to the network side device that beam failure recoverysucceeds.

Optionally, the UE 700 further includes:

a seventh processing module 714, configured to: when a beam failurerecovery procedure is stopped and/or a random access procedure in a beamfailure recovery procedure is stopped when a C-RNTI is monitored in thefirst CORESET, perform at least one of: determining that beam failurerecovery succeeds; indicating, by an MAC layer to a higher layer and/ora PHY layer, that beam failure recovery succeeds; stopping a beamfailure recovery timer; stopping a beam failure recovery requesttransmission counter; or stopping transmitting a random access preambleto the network side device.

Optionally, in a beam failure recovery procedure, the UE 700 furtherincludes:

an eighth processing module 715, configured to: when it is determinedthat CFRA fails, declare that beam failure recovery fails or continue arandom access procedure of beam failure recovery by using CBRA; or

when it is determined that CFRA fails and no indication of a candidatebeam and/or candidate resource from a PHY layer is received, declarethat beam failure recovery fails or continue a random access procedureof beam failure recovery by using CBRA; or

if a beam failure recovery timer expires in a beam failure recoveryprocedure and/or a preamble transmission or beam failure recoveryrequest transmission counter counts to a maximum value in a beam failurerecovery procedure, declare that beam failure recovery fails.

Optionally, the UE 700 further includes:

a ninth processing module 716, configured to: after a beam failure eventis triggered and/or an indication of a candidate beam and/or candidateresource from a PHY layer is received, start at least one of: a beamfailure recovery timer; a beam failure recovery request transmissioncounter; a CFRA-based beam failure recovery timer; a CFRA-based beamfailure recovery request transmission counter; a CBRA-based beam failurerecovery timer; or a CBRA-based beam failure recovery requesttransmission counter.

Optionally, the UE 700 further includes:

a tenth processing module 717, configured to: in the process ofcontinuing a random access procedure of beam failure recovery by usingCBRA, if a CBRA timer expires, and/or a CBRA preamble transmission orbeam failure recovery request transmission counter counts to a maximumvalue, declare that beam failure recovery fails.

Optionally, the UE 700 further includes:

an eleventh processing module 718, configured to: when a C-RNTI ismonitored in the first CORESET or the second CORESET before a beamfailure recovery timer expires, determine that beam failure recoverysucceeds; and/or

when a C-RNTI is monitored in the first CORESET or the second CORESETbefore a preamble transmission counter or a beam failure recoveryrequest transmission counter counts to a maximum value during beamfailure recovery, determine that beam failure recovery succeeds.

Optionally, the UE 700 further includes:

a fifth indication module 719, configured to: when beam failure recoveryfails or beam failure recovery succeeds, indicate, to a PHY layer and/ora higher layer, that beam failure recovery fails or beam failurerecovery succeeds.

Optionally, the UE 700 further includes:

a sixth indication module 720, configured to: when an MAC layerdetermines that beam failure recovery succeeds or beam failure recoveryfails, indicate, to an RRC layer, indication information indicating thatbeam failure recovery succeeds or beam failure recovery fails, where theindication information is used in the RRC layer for instructing the RRClayer to adjust RLM.

Referring to FIG. 8, the present disclosure provides in some embodimentsanother UE 800, including: at least one processor 801, a storage 802, auser interface 803, and at least one network interface 804. The variouscomponents in the UE 800 are coupled together by a bus system 805.

It may be understood that the bus system 805 is configured to implementconnection and communication among these components. The bus system 805further includes a power bus, a control bus, and a status signal bus inaddition to a data bus. However, for clarity, various buses in FIG. 8are all shown as the bus system 805.

The user interface 803 may include a display, a keyboard or apoint-and-click device (for example, a mouse, a trackball, a touchpanel, a touch screen or the like).

It may be understood that the storage 802 in some embodiments of thepresent disclosure may be a volatile storage or a nonvolatile storage ormay include both a volatile storage and a nonvolatile storage. Thenonvolatile storage may be a read-only memory (ROM), a programmable ROM(PROM), an erasable programmable PROM (EPROM), an electrically EPROM(EEPROM) or a flash memory. The volatile storage may be a random accessmemory (RAM), which is used as an external cache. By way of examplerather than limitation, many forms of RAMs such as a static RAM (SRAM),a dynamic RAM (DRAM), a synchronous DRAM (SDRAM), a double-data-rateSDRAM (DDRSDRAM), an enhanced SDRAM (ESDRAM), a Synchlink DRAM (SLDRAM),and a Direct Rambus RAM (DRRAM) may be used. The storage 802 describedin some embodiments of the present disclosure is intended to include,but is not limited to, these and any other suitable types of storages.

In some implementations, the storage 802 stores the following elements,executable modules or data structures or a subset thereof, or anextended set thereof: an operating system (OS) 8021 and an application8022.

The operating system 8021 includes various system programs such as aframework layer, a core library layer, and a driver layer, and isconfigured to implement various basic services and processhardware-based tasks. The application 8022 includes various applicationssuch as a media player or a browser, and is configured to implementvarious application services. A program for implementing the methodprovided in some embodiments of the present disclosure may be includedin the application 8022.

In some embodiments of the present disclosure, the UE 800 furtherincludes a computer program stored in the storage 802 and configured tobe executed by the processor 801. The processor 801 is configured toexecute the computer program to implement the steps of the methodprovided in some embodiments of the present disclosure.

The foregoing method disclosed in some embodiments of the presentdisclosure may be applied to the processor 801 or implemented by theprocessor 801. The processor 801 may be an integrated circuit chiphaving a signal processing capability. During implementation, the stepsin the foregoing method may be accomplished by hardware integrated logiccircuits or instructions in a software form in the processor 801. Theprocessor 801 may be a general-purpose processor, a digital signalprocessor (DSP), an application-specific integrated circuit (ASIC), afield-programmable gate array (FPGA) or another programmable logicdevice, discrete gate or transistor logic device, a discrete hardwarecomponent, that can implement or execute the methods, steps, and logicblock diagrams disclosed in some embodiments of the present disclosure.The general-purpose processor may be a microprocessor or the processormay be any conventional processor or the like. The steps in the methoddisclosed with reference to some embodiments of the present disclosuremay be directly performed and accomplished by a hardware decodingprocessor or performed and accomplished by a combination of hardware andsoftware modules in a decoding processor. The software modules may belocated in a computer-readable storage medium well-known in the art,such as a RAM, a flash memory, a ROM, a PROM or an electrically erasableprogrammable memory or a register. A computer-readable storage medium islocated in the storage 802. The processor 801 reads information in thestorage 802 and accomplishes the steps in the foregoing method incombination with hardware of the processor. Specifically, thecomputer-readable storage medium stores a computer program.

It may be understood that these embodiments described in this disclosuremay be implemented by using hardware, software, firmware, middleware,microcode or a combination thereof. For hardware implementation, aprocessing unit may be implemented in one or more of an ASIC, a DSP, aDSP device (DSPD), a programmable logic device (PLD), an FPGA, ageneral-purpose processor, a controller, a microcontroller, amicroprocessor, another electronic unit configured to perform thefunctions in the present application or a combination thereof.

For software implementation, the techniques in some embodiments of thepresent disclosure may be implemented by using modules (for example,processes or functions) that perform the functions in some embodimentsof the present disclosure. Software code may be stored in a storage andexecuted by a processor. The storage may be implemented internal orexternal to the processor.

The steps of the methods or algorithms described in the disclosedcontent of the present disclosure may be implemented in the form ofhardware or may be implemented in the form of software instructionsexecuted by a processor. The software instructions may be formed bycorresponding software modules. The software modules may be stored in aRAM, a flash memory, a ROM, an EPROM, an EEPROM, a register, a harddisk, a removable disk, a CD-ROM or any other form of storage mediumknown to persons skilled in the art. An exemplary storage medium iscoupled to the processor, so that the processor can read informationfrom the storage medium and can write information into the storagemedium. Certainly, the storage medium may alternatively be a part of theprocessor. The processor and the storage medium may be located in theASIC. In addition, the ASIC may be located in a core network interfacedevice. Certainly, the processor and the storage medium may also residein the core network interface device as discrete components.

Persons skilled in the art should be aware that in one or more examplesin the foregoing description, the functions described in the presentdisclosure may be implemented by using hardware, software, firmware orany combination thereof. When software is used for implementation, thesefunctions may be stored in a computer-readable medium or transmitted asone or more instructions or codes in the computer-readable medium. Thecomputer-readable medium includes a computer storage medium and acommunication medium. The communication medium includes any mediumfacilitating the transfer of a computer program from one place toanother place. The storage medium may be any available medium accessibleto a general-purpose or special-purpose computer.

In the foregoing specific implementations, the objectives, technicalsolutions, and benefits of the present disclosure are described indetail. It should be understood that the foregoing descriptions aremerely specific implementations of the present disclosure, and are notintended to limit the scope of the present disclosure. Any modification,equivalent replacement, or improvement made based on the technicalsolution of the present disclosure should fall within the scope of thepresent disclosure.

Persons skilled in the art should understand that some embodiments ofthe present disclosure may be provided as a method, a system or acomputer program product. Therefore, some embodiments of the presentdisclosure may adopt the form of hardware only embodiments, softwareonly embodiments, or embodiments combining software and hardware.Moreover, some embodiments of the present disclosure may adopt the formof a computer program product implemented on one or more computer-usablestorage media (including but not limited to a disk storage, a compactdisc read-only memory (CD-ROM), an optical storage or the like)including computer usable program code.

Some embodiments of the present disclosure are described with referenceto the flowcharts and/or block diagrams of the method, device (system),and computer program product according to some embodiments of thepresent disclosure. It should be understood that computer programinstructions may be used to implement each process and/or each block inthe flowcharts and/or the block diagrams and a combination of processesand/or blocks in the flowcharts and/or the block diagrams. Thesecomputer program instructions may be provided to a general-purposecomputer, a special-purpose computer, an embedded processor or aprocessor of other programmable data processing device to generate amachine, so that the instructions executed by a computer or a processorof other programmable data processing device generate an apparatus forimplementing a specific function in one or more processes in theflowcharts and/or in one or more blocks in the block diagrams.

These computer program instructions may also be stored in acomputer-readable storage that can instruct the computer or otherprogrammable data processing device to work in a specific manner, sothat the instructions stored in the computer-readable storage generatean artifact that includes an instruction apparatus. The instructionapparatus implements a specific function in one or more processes in theflowcharts and/or in one or more blocks in the block diagrams.

These computer program instructions may also be loaded onto a computeror other programmable data processing device, so that a series ofoperations and steps are performed on the computer or other programmabledevice, thereby generating computer-implemented processing. Therefore,the instructions executed on the computer or other programmable deviceprovide steps for implementing a specific function in one or moreprocesses in the flowcharts and/or in one or more blocks in the blockdiagrams.

Obviously, persons skilled in the art can make various modifications andvariations to some embodiments of the present disclosure withoutdeparting from the spirit and scope of the present disclosure. If thesemodifications and variations to some embodiments of the presentdisclosure fall within the scope of claims of the present disclosure andequivalents thereof, the present disclosure is also intended toencompass these modifications and variations.

What is claimed is:
 1. A beam failure recovery method, comprising: aftera beam failure event or a beam failure recovery event is triggered,monitoring a physical downlink control channel (PDCCH) scrambled with acell radio network temporary identifier (C-RNTI) in a first controlchannel resource set (CORESET) for beam failure recovery and monitoringa PDCCH scrambled with a C-RNTI in a second CORESET, wherein resourcescorresponding to the first CORESET are different from resourcescorresponding to the second CORESET; wherein the method furthercomprises: determining that the beam failure recovery succeeds anddiscarding a C-RNTI when the C-RNTI is monitored in the first CORESET,and continuing monitoring a C-RNTI in the second CORESET.
 2. The beamfailure recovery method according to claim 1, further comprising:stopping monitoring a PDCCH scrambled with a C-RNTI in the secondCORESET when a C-RNTI is monitored in the first CORESET; or stoppingmonitoring a PDCCH scrambled with a C-RNTI in the first CORESET when aC-RNTI is monitored in the second CORESET.
 3. The beam failure recoverymethod according to claim 1, wherein, before the monitoring the PDCCHscrambled with the C-RNTI in the first CORESET for beam failure recoveryand/or before the monitoring the PDCCH scrambled with the C-RNTI in thesecond CORESET, the method further comprises: indicating, by a mediaaccess control (MAC) layer, a beam failure indication to a physical(PHY) layer; or transmitting a random access preamble to a network sidedevice by using a random access procedure, wherein the random accesspreamble is used as a beam failure recovery request; or indicating, by aPHY layer, a candidate beam or a resource corresponding to a candidatebeam or a candidate resource to an MAC layer.
 4. The beam failurerecovery method according to claim 3, wherein before the transmittingthe random access preamble to the network side device by using therandom access procedure or before the indicating, by the PHY layer, thecandidate beam or the resource corresponding to the candidate beam orthe candidate resource to the MAC layer, the method further comprises atleast one of: stopping a beam failure recovery timer; stopping a beamfailure recovery request transmission counter; or stopping transmittinga random access preamble to the network side device.
 5. The beam failurerecovery method according to claim 3, wherein, after the transmittingthe random access preamble to the network side device by using therandom access procedure so as to transmit a beam failure recoveryrequest or after the indicating, by the PHY layer, the candidate beam orthe resource corresponding to the candidate beam or the candidateresource to the MAC layer, the method further comprises at least one of:stopping a beam failure recovery timer; stopping a beam failure recoveryrequest transmission counter; stopping transmitting a random accesspreamble to the network side device; or indicating to the network sidedevice that beam failure recovery succeeds.
 6. The beam failure recoverymethod according to claim 1, wherein, when a C-RNTI is monitored in thesecond CORESET, the method further comprises at least one of: continuinga beam failure recovery procedure; continuing a random access procedurein a beam failure recovery procedure; or indicating, by a physical (PHY)layer, a new candidate beam or candidate reference signal (RS) resourceto a media access control (MAC) layer.
 7. The beam failure recoverymethod according to claim 6, wherein the new candidate beam is a beam inthe second CORESET in which a C-RNTI is monitored; or the new candidateRS resource is an RS resource in the second CORESET in which a C-RNTI ismonitored.
 8. The beam failure recovery method according to claim 1,wherein when a C-RNTI is monitored in the second CORESET or when aphysical (PHY) layer determines that beam failure recovery succeeds inthe process of monitoring a C-RNTI in the first CORESET or the secondCORESET, the method further comprises at least one of: stopping a beamfailure recovery procedure; stopping a random access procedure in a beamfailure recovery procedure; or indicating, by a PHY layer to a higherlayer, that beam failure recovery succeeds.
 9. The beam failure recoverymethod according to claim 8, wherein, when indicating, by the PHY layerto the higher layer, that beam failure recovery succeeds, the methodfurther comprises at least one of: stopping a beam failure recoveryprocedure; or stopping a random access procedure in a beam failurerecovery procedure.
 10. The beam failure recovery method according toclaim 1, wherein, when a C-RNTI is monitored in the first CORESET, themethod further comprises at least one of: stopping a beam failurerecovery procedure; stopping a random access procedure in a beam failurerecovery procedure; determining that beam failure recovery succeeds;indicating, by a media access control (MAC) layer to a higher layerand/or a physical (PHY) layer, that beam failure recovery succeeds;stopping a beam failure recovery timer; stopping a beam failure recoveryrequest transmission counter; or stopping transmitting a random accesspreamble to a network side device.
 11. The beam failure recovery methodaccording to claim 1, wherein, in the process of monitoring a C-RNTI inthe first CORESET or the second CORESET, the method further comprises:when contention-free random access (CFRA) fails, declaring that beamfailure recovery fails or continuing a random access procedure of beamfailure recovery by using contention-based random access (CBRA); or whenCFRA fails and no indication of a candidate beam and/or candidateresource from a physical (PHY) layer is received, declaring that beamfailure recovery fails or continuing a random access procedure of beamfailure recovery by using CBRA; or if a beam failure recovery timerexpires in a beam failure recovery procedure and/or a preambletransmission or beam failure recovery request transmission countercounts to a maximum value in a beam failure recovery procedure,declaring that beam failure recovery fails; wherein that the CFRA failscomprises at least one of: a CFRA timer expires; or a CFRA preambletransmission counter reaches a maximum value.
 12. The beam failurerecovery method according to claim 11, wherein, after a beam failureevent or a beam failure recovery event is triggered and/or when anindication of a candidate beam and/or candidate resource is receivedfrom the PHY layer in the process of monitoring a C-RNTI in the firstCORESET or the second CORESET, the method further comprises starting atleast one of: a beam failure recovery timer; a beam failure recoveryrequest transmission counter; a CFRA-based beam failure recovery timer;a CFRA-based beam failure recovery request transmission counter; aCBRA-based beam failure recovery timer; or a CBRA-based beam failurerecovery request transmission counter.
 13. The beam failure recoverymethod according to claim 11, further comprising: in the process ofcontinuing a random access procedure of beam failure recovery by usingCBRA, if a CBRA timer expires, and/or a CBRA preamble transmission orbeam failure recovery request transmission counter counts to a maximumvalue, declaring that beam failure recovery fails.
 14. The beam failurerecovery method according to claim 1, further comprising: when a C-RNTIis monitored in the first CORESET or the second CORESET before a beamfailure recovery timer, a contention-free random access (CFRA)-basedbeam failure recovery timer or a contention-based random access(CBRA)-based beam failure recovery timer expires, determining that beamfailure recovery succeeds; and/or when a C-RNTI is monitored in thefirst CORESET or the second CORESET before a preamble transmissioncounter, a beam failure recovery request transmission counter, aCFRA-based beam failure recovery request transmission counter or aCBRA-based beam failure recovery request transmission counter counts toa maximum value during beam failure recovery, determining that beamfailure recovery succeeds.
 15. The beam failure recovery methodaccording to claim 11, further comprising: when beam failure recoveryfails or beam failure recovery succeeds, indicating, to a PHY layerand/or a higher layer, that beam failure recovery fails or beam failurerecovery succeeds.
 16. The beam failure recovery method according toclaim 1, further comprising: when a media access control (MAC) layerdetermines that beam failure recovery succeeds or beam failure recoveryfails, transmitting, to a radio resource control (RRC) layer, indicationinformation indicating that beam failure recovery succeeds or beamfailure recovery fails, wherein the indication information is used inthe RRC layer for indicating the RRC layer to adjust radio linkmonitoring (RLM).
 17. The beam failure recovery method according toclaim 1, wherein the resources corresponding to the first CORESETcomprise at least one of: all candidate beams; reference signal (RS)resources corresponding to all candidate beams; some candidate beams; RSresources corresponding to some candidate beams; a candidate RSresource; or a candidate RS resource corresponding to a candidate beam.18. User equipment (UE), comprising a processor, a storage, and acomputer program stored in the storage and configured to be executed bythe processor, wherein the processor is configured to execute thecomputer program to implement the steps in the beam failure recoverymethod according to claim
 1. 19. A non-transitory computer-readablestorage medium, storing therein a computer program, wherein the computerprogram is configured to be executed by a processor to implement thesteps in the beam failure recovery method according to claim 1.